Update to apache lucene 10.X#9205
Closed
matthiasblaesing wants to merge 13 commits intoapache:masterfrom
Closed
Conversation
Contributor
matthiasblaesing
commented
Feb 13, 2026
matthiasblaesing
commented
- Additional package lucene-analysis-common required (KeywordAnalyzer, WhitespaceAnalyzer, PerFieldAnalyzerWrapper, CharTokenizer, LimitTokenCountAnalyzer)
- FieldTypes were introduced to carry the field behavior (tokenization state, indexing options, storage settings)
- BooleanQuery construction moved to builder
- Collector interface was modified
- TermEnum was replaced by TermsEnum
- Terms are stored per field, so queries have to be specified with the target field
- QuerySelectors were replaced by String sets
- RAMDirecory was removed and is replaced by ByteBufferDirectories
- Lock handling was reworked
new test and build range: JDK 21-26 few modules are still stuck on 17 and got special treatment
- added unimportant classes to the ignore list so that the test data doesn't have to be updated. - refactored file read monitoring from SecurityManager to JFR
- remove no longer needed SM usage in ide/xsl test - remove NBBundleWithSecurityManager test - remove NbLifecycleManagerEDTTest which is similar to LifecycleManagerEDTTest in openide.util.ui
matthiasblaesing
added
PHP
matthiasblaesing
force-pushed
the
update-lucene2
branch
from
2b18d19 to
7ef490c
Compare
mbien
added
Upgrade Library
matthiasblaesing
force-pushed
the
update-lucene2
branch
from
7ef490c to
0235bde
Compare
- Additional package lucene-analysis-common required (KeywordAnalyzer, WhitespaceAnalyzer, PerFieldAnalyzerWrapper, CharTokenizer, LimitTokenCountAnalyzer) - FieldTypes were introduced to carry the field behavior (tokenization state, indexing options, storage settings) - BooleanQuery construction moved to builder - Collector interface was modified - TermEnum was replaced by TermsEnum - Terms are stored per field, so queries have to be specified with the target field - QuerySelectors were replaced by String sets - RAMDirecory was removed and is replaced by ByteBufferDirectories - Lock handling was reworked
matthiasblaesing
force-pushed
the
update-lucene2
branch
from
0235bde to
54bc32a
Compare
Member
|
The repo is likely not ready yet for a core JDK 21 dependency like lucene 10.x (#7871). Lucene 9.x uses JDK 11 as baseline which would avoid a bunch of problems as intermediate step (+ we already use it elsewhere too). Both @lkishalmi and me tried to stabilize on lucene 4 first, I haven't touched my wip branch in a while but I believe Laszlo is experimenting right now with lucene 4 too. |
Contributor
Author
|
Ok, given the reliance of enterprise and graalvm tests on JDK 17 I'll close this one. I'll mark the Lucene 9 one as draft. I think the remaining problem is, that the locking logik is off somewhere and now that lucene verifies lock it is caught. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.